% \documentclass[preprint,11pt]{elsarticle}
% 
%
%
%\begin{document}
% 
%\begin{frontmatter}
%\title{Disciplined Structured Communications with \\ 
%%Consistent
%Disciplined Runtime Adaptation}
%%\title{Disciplined Adaptation for Structured Communications}
%\author[evry]{Cinzia Di Giusto} 
%\author[unl]{Jorge A. P\'{e}rez}
%
%%\cortext[cor1]{Corresponding author}  
%\address[evry]{Universit\'e d'Evry - Val d'Essonne, IBISC}
%\address[unl]{CITI and Departamento de Inform\'atica, FCT Universidade Nova de Lisboa}



\title{Modular, Event-based Runtime Adaptation  for Communication-Centric Systems: A Conceptual Framework}
\author{
        Cinzia Di Giusto \\
                Universit\'e d'Evry - Val d'Essonne, Laboratoire IBISC \\ France
            \and
        Jorge A. P\'{e}rez\\
      CITI and Departamento de Inform\'atica \\ FCT Universidade Nova de Lisboa, Portugal
}
\date{\today}

\documentclass[11pt]{article}

\usepackage{intestazione2}
\usepackage{macron}
\usepackage{typecasemacro}
\usepackage{geometry}
\usepackage{enumerate}
\usepackage{times}
\usepackage{mathpartir}


\begin{document}
\maketitle


     
\begin{abstract}
We propose a formal architectural framework for specifying and reasoning about \emph{robust} com\-mu\-ni\-ca\-tion-centric systems, specified 
as $\pi$-calculus processes. Our framework suggests an organization in which the communication part of the system
is modularly isolated from the program components handling runtime adaptation requests, which may come from inside the system or from external requirements.
We choose an event-based approach to connect behavioral and reconfiguration components in an uniform way.
A significant advantage of adopting our framework is that it allows reuse of existing behavioral type disciplines for correct communications,
treating error handling and recovery as an orthogonal issue. To illustrate our conceptual framework, we consider a number of exceptional circumstances that may occur at runtime, ranging from application migration until rollback, and describe how they are 
handled in our setting.
\end{abstract}

\section{Motivations}
\input{motivation}


\input{notes}


%\section{Introduction}
%\input{intro}

\section{A Process Language with Runtime Adaptation}\label{sec:syn}
%\input{calculi}

%\section{The Type System}\label{s:types}
%\input{newtype}
%
%\section{Session Safety and Consistency by Typing}\label{sec:res}
%\input{theorems}
%
%\section{Example: An Adaptable Client/Service Scenario}\label{sec:exam}
%\input{exserver}
%
%\section{Discussion: Towards More Flexible Interfaces}\label{sec:int}
%\input{interface}
%
%\section{Related Work}\label{sec:rw}
%\input{conclud}
%
%{\small
%\bibliographystyle{abbrv}
%\bibliography{referen}
%}

\end{document}